Harden Public Preview and alpha bootstrap gates - #8
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
live-smokeandnpmenvironment reviewer configuration comments0.1.0-alpha.1onnextWhy
The standalone scan previously ran only as part of the expensive copied-repository check, so
check:public-previewcould pass without reporting outside-root content. The documented alpha.1 token exception was also not executable, and two workflow comments contradicted the accepted environment reviewer policy.Impact
Public Preview validation now reports identity, public-content, and standalone-content violations together. Trusted Publishing remains the default npm path; the bootstrap secret is injected only when the protected environment explicitly enables it for exactly
0.1.0-alpha.1.Verification
npm cinpm run verifynpm run check:standalone-contentnpm audit --omit=dev --json(0 production vulnerabilities)git diff --checkNo repository visibility, tag, release, live API, npm publication, secret, or repository setting was changed.